Bumps [path-parse](https://github.com/jbgutierrez/path-parse) from 1.0.6 to 1.0.7.
- [Release notes](https://github.com/jbgutierrez/path-parse/releases)
- [Commits](https://github.com/jbgutierrez/path-parse/commits/v1.0.7)

---
updated-dependencies:
- dependency-name: path-parse
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

…lue is present)

- Integrate testing-library

…custom input as well.

…rmat

Test upgrade

fix: `onValueChange` not called for values with 3 or less characters

s-yadav#839

…adav#851

…Format as its a number_format base props and shouldn't be used outside. s-yadav#850

…#849

Fix Number Formatting Order in Customization

Handle caret position when fixedDecimalScale is used and user types after clearing input.

chore(react-version): upgrade peer react version to include react 19

doc: fix spelling of `PatternFormat`

The return type of `NumericFormat` and `PatternFormat` was being inferred as
`JSX.Element` which caused the following type error (typescript v5.7.3):

```
error TS2786: 'PatternFormat' cannot be used as a JSX component.
  Its type '<BaseType = InputAttributes>(props: PatternFormatProps<BaseType>) => Element' is not a valid JSX element type.
    Type '<BaseType = InputAttributes>(props: PatternFormatProps<BaseType>) => Element' is not assignable to type '(props: any) => ReactNode | Promise<ReactNode>'.
      Type 'Element' is not assignable to type 'ReactNode | Promise<ReactNode>'.
        Property 'children' is missing in type 'Element' but required in type 'ReactPortal'.
```

Instead of being inferred, explicitly add the return type of `React.ReactElement`
which represents a JSX element.

fix: add explicit return types